Initiating application execution with trigger characters

ABSTRACT

Disclosed are various embodiments for initiating execution of an application using trigger characters. In one embodiment, a computing device detects an entry of a trigger character in an input field of a first user interface presented by a first application. The input field is specified for detection of the individual trigger character based on a trigger rule for the first application. The computing device then identifies a string following the trigger character. The computing device then determines that the string matches a name of a second application installed on the computing device based on a list of applications installed on the computing device. The computing device then initiates execution of the second application. Subsequently, the computing device switches from the first user interface to a second user interface presented by the second application.

CROSS-REFERENCE TO RELATED TO RELATED APPLICATION

This application is a continuation of and claims the benefit of U.S.patent application Ser. No. 15/417,247, entitled “INITIATING APPLICATIONEXECUTION WITH TRIGGER CHARACTERS” and filed Jan. 27, 2017, which ishereby incorporated by reference in its entirety.

BACKGROUND

Mobile computing devices, such as smartphones and tablet computers, areoften configured to execute applications in isolation of each other bydefault. For example, Apple's iOS® operating system is configured toexecute each application in a separate sandboxed environment. As aconsequence, applications are often, by default, unable to communicateor share data with each other. For example, files saved by oneapplication may not be visible or available to another application. Asanother example, interprocess communications between applications may beprohibited by default.

Some operating systems, however, provide mechanisms for separateapplications to communicate with each other. For example, in iOS,applications can optionally implement extensions. In iOS, extensionsprovide an interface for a second application to send data to orinteract with the application implementing an extension. For example, anelectronic mail (e-mail) application could implement an extensionallowing other applications to create a new e-mail message with a fileattached or to create a new e-mail message to a particular person.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following drawings. The components in the drawings arenot necessarily to scale, with emphasis instead being placed uponclearly illustrating the principles of the disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1A depicts an example of a user interface.

FIG. 1B depicts an example of a user interface.

FIG. 1C depicts an example of a user interface.

FIG. 2 depicts a computing device.

FIG. 3 depicts a flowchart of a component of the computing device ofFIG. 2.

DETAILED DESCRIPTION

Disclosed are various approaches for accessing a user interface of asecond application from within a user interface of a first application.For example, in iOS, an application may implement an extension thatallows other applications to communicate with it. For instance, ane-mail application could implement an extension that allows a documentstorage application or another document provider application to create anew e-mail message with a file attached. This functionality can beaccessed from within the document storage application, for example, byselecting a file and then selecting an option to attach the file to anemail. Accordingly, the document storage application, document provider,or similar document storage application is able to push, provide, orotherwise send the file to the e-mail application. In some instances,the document storage application can also trigger the user interface ofthe email application to open in order for the user to input addressesof the recipients, a subject, a message, and other data. However, a userwithin the e-mail application would not necessarily be able to attach orrequest a document from the document storage application becauseapplication extensions do not provide for bi-directional communication.So, while an application in iOS that implements an extension can receiveinformation from another application, it cannot request or retrieveinformation from the other application.

As an example, if the user had the email application open in iOS, theuser would not be able to request a file from a second application, suchas a document storage application, to attach to an email message.Instead, the user would have to exit the email application and open thedocument storage application to access a file for attachment to an emailmessage. The user would then need to select the file in the documentstorage application and select the extension provided by the e-mailapplication to attach the file to an e-mail. This could then trigger thee-mail application to relaunch with a new message window alreadydisplayed and the selected file already attached to the new e-mail.Various embodiments of the present disclosure simplify this workflow. Inthe following discussion, a general description of the system and itscomponents is provided, followed by a discussion of the operation of thesame.

FIG. 1A depicts a first user interface 103 a provided by an e-mailapplication executing on a mobile computing device 106. For example, thefirst user interface 103 a could correspond to a message compositioninterface of the e-mail application bundled with iOS. Within the firstuser interface 103 a are a number of user interface elements, such asfield for listing recipients, a field listing the sender's emailaddress, a field for the subject of the e-mail, and a field for the bodyof the e-mail. Within the body of the email, a user has entered atrigger character 109, followed by a string that identifies a name of asecond application (e.g., “DocumentLocker”) installed on the mobilecomputing device 106. Although the depicted trigger character 109 is the“@” symbol, any text character could be used and different textcharacters could be used and may be more appropriate in differentcontexts. For example, some embodiments may use non-alphanumericcharacters (e.g., punctuation marks, symbols, etc.) because they areused less frequently than letters and numbers. As later described, entryof the trigger character 109 causes the specified application to belaunched, allowing a user to launch a second application from within theuser interface of a first application.

In the example depicted in FIG. 1A, the user is composing an e-mail toseveral recipients and wishes to attach several files to the e-mail. Inorder to access the files, the user has entered the trigger character109, followed by the name of the application where the files can beaccessed (e.g., “Document storage application”). This allows a user todirectly open a second application from within a first application.

FIG. 1B depicts a second user interface 103 b of a second application,such as a document storage application, installed on the mobilecomputing device 106. As depicted, the user is able to select severalfiles. A list of potential actions 113 provided by the e-mailapplication through an application extension is also shown. The usercould then, for example, select the “Attach” action 113 to attach theselected files to the email the user was composing previously in FIG.1A.

FIG. 1C depicts a user interface 103 a of the first application after auser has selected one or more files as attachments to an email in themanner depicted previously in FIG. 1A and FIG. 1B. As depicted, a listof attached files 116 is provided at the bottom of the e-mail. Thesefiles can correspond to the files previously selected with the userinterface 103 b depicted in FIG. 1B.

With reference to FIG. 2, shown is a computing device 203. The computingdevice 203 can be embodied in the form of a personal computer (e.g., adesktop computer, a laptop computer, or similar device), a mobilecomputing device 106 (e.g., personal digital assistants, cellulartelephones, smartphones, web pads, tablet computer systems, musicplayers, portable game consoles, electronic book readers, and similardevices), media playback devices (e.g., media streaming devices, BluRay®players, digital video disc (DVD) players, set-top boxes, and similardevices), a videogame console, or other devices with like capability.The computing device 203 can include one or more displays, such asliquid crystal displays (LCDs), gas plasma-based flat panel displays,organic light emitting diode (OLED) displays, electrophoretic ink(“E-ink”) displays, projectors, or other types of display devices.

The computing device 203 can be configured to execute variousapplications such as a monitor application 206, one or more clientapplications 209, or other applications. The monitor application 206 isexecuted to detect entry of a trigger character 109 in the userinterface of a first client application 209 and initiate execution of asecond client application 209 identified with the trigger character 109.The client applications 209 can be executed by the computing device 203,causing a user interface to be rendered on the display. To this end,client applications 209 can include, for example, a browser, an e-mailapplication, a social networking application, a document storageapplication or document storage provider, a word processor, aspreadsheet, a game, a photo editor, a calendar application, or otherapplication.

The monitor application 206 can be configured to monitor charactersentered into the user interface of an application using variousapproaches. As a first example, the monitor application 206 could beprovided with permissions to access or view characters entered with thekeyboard. For instance, various operating systems for mobile computingdevices may not allow an application to view keystrokes entered througha keyboard interface unless the application has been granted permissionto do so. As a second example, the client application 209 could beconfigured to send characters it receives from a keyboard to the monitorapplication 206. For example, the monitor application 206 could beintegrated into the client application 209 or the client application 209and monitor application 206 could be configured to communicate with eachother via various interprocess communication mechanisms (e.g., sharedfiles, shared memory, sockets, etc.).

Also, various data is stored in a data store 213 that is accessible tothe computing device 103. The data store 213 can be representative of aplurality of data stores 213, which can include relational databases,object-oriented databases, hierarchical databases, hash tables orsimilar key-value data stores, as well as other data storageapplications or data structures. The data stored in the data store 213is associated with the operation of the monitor application 206, asdescribed later. This data can include a list of installed applications216, one or more trigger rules 219, and potentially other data.

The list of installed applications 216 includes the name of each clientapplication 209 installed on the computing device 203. In someinstances, the list of installed applications 216 can identifyapplication groups as well as which of the installed client applications209 are within each application group. Some systems, such as iOS,provide for applications groups, which define sets of clientapplications 209 that are allowed to access a common shared path orfolder in a filesystem of the computing device 203. Data saved in thecommon shared path or folder by one client application 209 in anapplication group can be accessed by any other client application 209 inthe same application group. Other systems may provide similarfunctionality.

The trigger rules 219 can be used to define specific trigger characters109 individual client applications 209 and how trigger characters 109should be processed for a specific client application 209. For example,a first trigger rule 219 could specify the “@” symbol as a triggercharacter 109 for a first client application 209 and the “$” as atrigger character 109 for a separate, second client application 209. Asanother example, a trigger rule 219 could specify that a triggercharacter 109 should only be recognized in a specific text field, userinterface element, or user interface context. For instance, a triggerrule 219 for an email application could specify that a trigger character109 should only initiate execution of a second client application 209 ifthe trigger character 109 is entered within the body of an e-mail.

A trigger rule 219 could also specify how a second client application209 to be executed is identified with the trigger character 109. Forexample, the trigger rule 219 could specify that the string of textimmediately following the trigger character is to be used to identifythe client application 209 to be executed. In this example, the triggerrule 219 could also specify that the string of text is terminated with acharacter (e.g., a formatting character such as a space, tab, or anewline character, a punctuation mark, etc.). As a second example, thetrigger rule 219 could specify a regular expression. Any string of textmatching the regular expression would be a potential identifier of theclient application 209 to be executed. In some instances, the triggerrule 219 can also specify how to identify arguments to be passed to aclient application 209 being invoked with a trigger character 109.

To briefly describe the operation of the components of the computingdevice 203, the monitor application 206 detects an entry of a triggercharacter 109 within a first user interface presented by a first clientapplication 209 installed on the computing device 203 (e.g., a mobilecomputing device 106). In some instances, the monitor application 206can determine that the entry of the trigger character 109 is within apermitted text field within the first user interface of the first clientapplication 209. In these instances, the monitor application 206 mayignore the trigger character 109 and decline to process the triggercharacter 109 unless the trigger character 109 is within a permittedtext field.

The monitor application 206 then identifies a string following thetrigger character 109. In some instances, the monitor application 206can identify the string based at least in part on the entry of thetrigger character 109 occurring within the permitted text field of thefirst user interface presented by the first client application 209. Insome instances, the monitor application 206 can determine that thestring matches a name of a second client application 209 installed onthe computing device 203.

The monitor application 206 can then initiate execution of the secondclient application 209. In some instances, the monitor application 206can further identify a second string following the trigger character 109and provide the second string as an argument to the second clientapplication 209. In other instances, the monitor application 206 cancapture data from the first client application 209 based at least inpart on the name of the second client application 209. For example, ifthe name of the second client application 209 corresponds to a calendarapplication, the monitor application 206 may capture from the firstclient application 209 information about a proposed event in order toprepopulate one or more fields in the calendar application. The monitorapplication 206 can then provide the captured data to the second clientapplication 209.

Subsequently, the monitor application 206 may cause the computing device203 to switch from rendering the first user interface corresponding tothe first client application 209 to a second user interface presented bythe second client application 209. For example, the monitor application206 may send a signal to the first client application 209 to suspendexecution. As a second example, the monitor application 206 could adjustthe priority of the second client application 209 to supersede thepriority of the first client application 209. As a third example, themonitor application 206 could invoke a function provided by an API ofthe operating system of the computing device 203 to initiate a switchfrom the user interface of the first application to the user interfaceof the second application.

Various other approaches may be used depending on the particularoperating system or environment of the computing device 203.

Referring next to FIG. 3, shown is a flowchart that provides one exampleof the operation of a portion of the monitor application 206. It isunderstood that the flowchart of FIG. 3 provides merely an example ofthe many different types of functional arrangements that can be employedto implement the operation of the monitor application 206. As analternative, the flowchart of FIG. 3 can be viewed as depicting anexample of elements of a method implemented in the computing device 203.

Beginning with step 303, the monitor application 206 identifies all ofthe client applications 209 currently installed on the computing device203. For example, the monitor application 206 could query or otherwiseprocess the list of installed applications 216 stored in the data store213 of the computing device 203. In this example, the monitorapplication 206 could invoke a function available through an applicationprogramming interface (API) provided by an operating system of thecomputing device 203 that returns a list of all client applications 209installed on the computing device 203. In alternative embodiments, themonitor application 206 could, for example, iterate through a filesystemlocation (e.g., a directory) where client applications 209 are installedin order to identify all of the installed client applications 209.

Moving on to step 306, the monitor application 206 detects the entry ofa trigger character 109 within a first user interface provided by afirst client application 209. In one instance, the monitor application206 could monitor all characters entered into the first user interfaceand identify the trigger character 109 specified by a trigger rule 219from the stream of characters. In another instance, the monitorapplication 206 could monitor the characters entered into the first userinterface based at least in part on one or more criteria specified by atrigger rule 219. For example, the monitor application 206 could monitorthe set of characters, if any, entered into a particular user interfaceelement, text field, or user interface context specified by a triggerrule 219.

Proceeding next to step 309, the monitor application 206 determines thatthe client application 209 specified by the user with the triggercharacter 109 is included in the list of installed client applications209 previously identified at step 303. For example, the monitorapplication 206 could parse the text entered by the user in the mannerspecified by a respective trigger rule 219. For instance, the monitorapplication 206 could extract the characters immediately following thetrigger character 109 through a terminating character specified by thetrigger rule 219 (e.g., a formatting character such as a space, tab, ora newline character, a punctuation mark, etc.). In another instance, themonitor application 206 could determine whether any set of charactersentered by the user matches a regular expression specified by thetrigger rule 219.

In either case, the monitor application 206 could then determine whetherthe identified text associated with the trigger character 109 matches aname of a client application 209 installed on the computing device 203.For example, the monitor application 206 could iterate through the listof installed client applications 209 and determine whether theidentified text string matches a string representing a name of aninstalled client application 209. Assuming that a match is found, theprocess proceeds to step 313. However, if the identified text fails tomatch the name of a client application 209, the monitor application 206may wait

Referring to step 313, the monitor application 206 initiates executionof the client application 209 specified using the trigger character 109.For example, the monitor application 206 can request that the operatingsystem of the computing device 203 begin executing a binary applicationexecutable corresponding to the name of the client application 209 inthe list of installed applications that matches the name of the clientapplication 209 specified using the trigger character 109.

Moving on to step 316, the monitor application 206 can capture data fromthe first client application 209 which received the trigger character109. Many different types of data could be captured from the firstclient application 209. For example, application data such as the threadidentifier or process identifier can be captured from the first clientapplication 209. As another example, some or all of the data processedby the first client application 209 could be captured based on theidentity of the second client application 209. For example, if a userused a trigger character 109 to open a calendar application, the monitorapplication 206 could capture event data from the first clientapplication 209. As a second example, if a user entered a triggercharacter 109 to open an address book application, the monitorapplication 206 could capture contact information for an individual fromthe first client application 209. As a third example, if a user entereda trigger character 109 to open a browser, the monitor application 206could capture a link or uniform resource locator (URL) from the firstclient application 209. It should be noted that these examples areintended to illustrative and non-limiting—other types of data could becaptured by the monitor application 206 as appropriate.

In some instances, the data captured from the first client application209 could include one or more arguments to be passed to the secondclient application 209. For example, a browser could be passed a flag toenable private browsing (e.g., disabling browser history, cookies,etc.). As another example, an e-mail application could be passed a flagto encrypt an e-mail for the recipient instead of sending the e-mail ina plaintext form. In a third example, a calendar application could bepassed a flag specifying which calendar (e.g., work, personal, etc.)should be loaded. Moreover, multiple flags may be passed to individualclient applications 209.

Proceeding next to step 319, the monitor application 206 provides thecaptured data to the client application 209 specified with the triggercharacter 109. For example, the monitor application 206 could provide athread or process identifier to the second client application 209 inorder to identify the first client application 209 that was used toinvoke execution of the second client application 209. This informationcould be used, for instance, by the second client application 209 toenable a user to return directly to the first client application 209once he or she has completed one or more tasks with the second clientapplication 209. For example, once the second client application 209finishes executing, it could provide the thread or process identifier ofthe first client application 209 to the operating system of thecomputing device 203 (e.g., as an argument to an API call) to cause theoperating system of the computing device 203 to switch back to executingthe first client application 209 once the second client application 209has finished.

The operating system could determine that the second client application209 has finished executing in a number of ways. For instance, theoperating system could detect a user interaction signaling that the userhas finished performing his or her desired task (e.g., selecting filesto attach to an email, selecting contacts from an address book forcreating a meeting, etc.). The user interaction could includemanipulating a portion of the user interface of the second clientapplication 209 (e.g., pressing a button to indicate completion),pressing a button on the computing device 203, or other interaction. Inanother instance, the operating system could determine that the secondclient application 209 has finished execution by determining that thesecond client application 209 has completed execution based on an APIcall made by the second client application 209 (e.g., due to the secondclient application 209 invoking the “exit” API function).

In another example, could provide data extracted from the first clientapplication 209 to the second client application 209 in order toprepopulate fields or assist the user in completing a task. Forinstance, if a user used a trigger character 109 to open a calendarapplication, the monitor application 206 could supply data captured fromthe first client application 209 about an event (e.g., meeting,birthday, wedding, appointment, etc.) to the second client application209 in order to prepopulate one or more data fields in calendar entry.This information could be provided as an argument in a function callused by the first client application 209 to initiate execution of thesecond client application 209. This information could also be providedusing a function provided by an API of the operating system.Alternatively, this information could be provided by saving the data toa file that both the first and second client applications 209 havepermissions to access (e.g. applications within the same applicationgroup on iOS devices). In another instance, if a user used a triggercharacter 109 to open an address book application, the monitorapplication 206 could provide contact information for an individualcaptured from the first client application 209 to the second clientapplication 209 in order to prepopulate one or more fields in a newcontact entry. In a third instance, if a user used a trigger character109 to open a browser, the monitor application 206 could provide a linkor uniform resource locator (URL) captured from the first clientapplication 209 to the second client application 209 in order toautomatically create a bookmark or automatically load a web page.

Finally, at step 323, the monitor application 206 can cause thecomputing device 203 to switch presenting the user interface (e.g., userinterface 103 a) of the first client application 209 to presenting theuser interface (e.g., user interface 103 b) of the second clientapplication 209. For example, the monitor application 206 can send asignal to the first client application 209 to suspend execution. As asecond example, the monitor application 206 could adjust the priority ofthe second client application 209 to supersede the priority of the firstclient application 209. Various other approaches may be used dependingon the particular operating system or environment of the computingdevice 203.

After causing the computing device 203 to switch from presenting theuser interface of the first client application 209 to the user interfaceof the second client application 209, the process ends. Although thecomputing device 203 may switch back to presenting the user interface ofthe first client application 209 after a user finishes interacting withthe second client application 209, this last context switch is a resultof the second client application 209 returning control of the computingdevice 203 to the first client application 209. For example, the secondclient application 209 may specify the thread identifier or processidentifier provided previously in step 319 as the client application 209that should resume execution after execution of the second clientapplication 209 terminates.

The flowchart of FIG. 3 shows an example of the functionality andoperation of an implementation of portions of the monitor application206. The described components can be embodied in hardware, software, ora combination of hardware and software. If embodied in software, eachelement can represent a module of code or a portion of code thatincludes program instructions to implement the specified logicalfunction(s). The program instructions can be embodied in the form ofsource code that includes human-readable statements written in aprogramming language or machine code that includes machine instructionsrecognizable by a suitable execution system, such as a processor in acomputer system or other system. If embodied in hardware, each elementcan represent a circuit or a number of interconnected circuits thatimplement the specified logical function(s).

Although the flowchart of FIG. 3 shows a specific order of execution, itis understood that the order of execution can differ from that which isshown. The order of execution of two or more elements can be switchedrelative to the order shown. Also, two or more elements shown insuccession can be executed concurrently or with partial concurrence.Further, in some examples, one or more of the elements shown in thesequence diagrams can be skipped or omitted. In addition, any number ofcounters, state variables, warning semaphores, or messages could beadded to the logical flow described herein, for purposes of enhancedutility, accounting, performance measurement, or troubleshooting aid. Itis understood that all of these variations are within the scope of thepresent disclosure.

The individual components of the monitoring application 206 can eachinclude at least one processing circuit. The processing circuit caninclude one or more processors and one or more storage devices that arecoupled to a local interface. The local interface can include a data buswith an accompanying address/control bus or any other suitable busstructure. The one or more storage devices for a processing circuit canstore data or components that are executable by the one or processors ofthe processing circuit. Also, a data store can be stored in the one ormore storage devices.

The monitor application 206, and other components described herein, canbe embodied in the form of hardware, as software components that areexecutable by hardware, or as a combination of software and hardware. Ifembodied as hardware, the components described herein can be implementedas a circuit or state machine that employs any suitable hardwaretechnology. The hardware technology can include one or moremicroprocessors, discrete logic circuits having logic gates forimplementing various logic functions upon an application of one or moredata signals, application specific integrated circuits (ASICs) havingappropriate logic gates, programmable logic devices (for example,field-programmable gate array (FPGAs), and complex programmable logicdevices (CPLDs)).

Also, one or more or more of the components described herein thatinclude software or program instructions can be embodied in anynon-transitory computer-readable medium for use by or in connection withan instruction execution system such as a processor in a computer systemor other system. The computer-readable medium can contain, store, ormaintain the software or program instructions for use by or inconnection with the instruction execution system.

The computer-readable medium can include physical media, such as,magnetic, optical, semiconductor, or other suitable media. Examples of asuitable computer-readable media include, but are not limited to,solid-state drives, magnetic drives, flash memory. Further, any logic orcomponent described herein can be implemented and structured in avariety of ways. One or more components described can be implemented asmodules or components of a single application. Further, one or morecomponents described herein can be executed in one computing device orby using multiple computing devices.

The above-described examples of the present disclosure are merelyexamples of implementations to set forth for a clear understanding ofthe principles of the disclosure. Many variations and modifications canbe made to the above-described examples without departing substantiallyfrom the spirit and principles of the disclosure. All of thesemodifications and variations are intended to be included herein withinthe scope of this disclosure.

Therefore, the following is claimed:
 1. A non-transitory computerreadable medium comprising machine readable instructions that, whenexecuted by a processor, cause a computing device to at least: detect anentry of an individual trigger character in a user interface input fieldof a first user interface, the first user interface being generated by afirst application installed on the computing device, and the userinterface input field being specified for detection of the individualtrigger character based on a trigger rule for the first application;identify a string following the individual trigger character in responseto detection of the entry of the individual trigger character; determinethat the string matches a name of a second application installed on thecomputing device based on a list of applications installed on thecomputing device, wherein the name of the second application is includedin the list of installed applications; execute the second applicationwith the processor of the computing device; and display a second userinterface generated by the second application.
 2. The non-transitorycomputer readable medium of claim 1, wherein the machine readableinstructions, when executed by the processor, further cause thecomputing device to at least: determine a data type of data to capturefrom the first application based on the name of the second application;capture the data from the first application based on the determinationof the data type to be captured from the first application; and causethe captured data to be accessible to the second application.
 3. Thenon-transitory computer readable medium of claim 1, wherein the machinereadable instructions, when executed by the processor, further cause thecomputing device to at least: detect a completion of the execution ofthe second application; and return to an execution of the firstapplication based on the completion of the execution of the secondapplication.
 4. The non-transitory computer readable medium of claim 3,wherein the return to the execution of the first application is based onproviding a process identifier of the first application to the secondapplication in an instance in which the computing device has initiatedthe execution of the second application.
 5. The non-transitory computerreadable medium of claim 3, wherein the detection of the completion ofthe execution of the second application is based on at least one of auser interaction signaling a task completion or a user-manipulation of abutton for the computing device.
 6. The non-transitory computer readablemedium of claim 1, wherein the display of the second user interfacecomprises prepopulating the captured data from the first application. 7.The non-transitory computer readable medium of claim 1, wherein theidentification of the string is further based on a termination characterthat is specified by the trigger rule.
 8. A system, comprising: acomputing device comprising a processor and a memory; and machinereadable instructions stored in the memory that, when executed by theprocessor, cause the computing device to at least: detect an entry of anindividual trigger character in a user interface input field of a firstuser interface, the first user interface being generated by a firstapplication installed on the computing device, and the user interfaceinput field being specified for detection of the individual triggercharacter based on a trigger rule for the first application; identify astring following the individual trigger character in response todetection of the entry of the individual trigger character; determinethat the string matches a name of a second application installed on thecomputing device based on a list of applications installed on thecomputing device, wherein the name of the second application is includedin the list of installed applications; execute the second applicationwith the processor of the computing device; and display a second userinterface generated by the second application.
 9. The system of claim 8,wherein the machine readable instructions, when executed by theprocessor, further cause the computing device to at least: determine adata type of data to capture from the first application based on thename of the second application; capture the data from the firstapplication based on the determination of the data type to be capturedfrom the first application; and cause the captured data to be accessibleto the second application.
 10. The system of claim 8, wherein the stringcomprises a first string and the machine readable instructions, whenexecuted by the processor, further cause the computing device to atleast: detect a completion of the execution of the second application;and return to an execution of the first application based on thecompletion of the execution of the second application.
 11. The system ofclaim 10, wherein the return to the execution of the first applicationis based on providing a process identifier of the first application tothe second application in an instance in which the computing device hasinitiated the execution of the second application.
 12. The system ofclaim 10, wherein the detection of the completion of the execution ofthe second application is based on at least one of a user interactionsignaling a task completion or a user-manipulation of a button for thecomputing device.
 13. The system of claim 8, wherein the display of thesecond user interface comprises prepopulating the captured data from thefirst application.
 14. The system of claim 8, wherein the identify thestring is further based on a termination character that is specified bythe trigger rule.
 15. A method, comprising: detecting, by a computingdevice, an entry of an individual trigger character in a user interfaceinput field of a first user interface, the first user interface beinggenerated by a first application installed on the computing device, andthe user interface input field being specified for detection of theindividual trigger character based on a trigger rule for the firstapplication; identifying, by the computing device, a string followingthe individual trigger character in response to detection of the entryof the individual trigger character; determining, by the computingdevice, that the string matches a name of a second application installedon the computing device based on a list of applications installed on thecomputing device, wherein the name of the second application is includedin the list of installed applications; causing, by the computing device,the second application to be executed by the computing device; anddisplaying, by the computing device, a second user interface generatedby the second application.
 16. The method of claim 15, furthercomprising: determining, by the computing device, a data type of data tocapture from the first application based on the name of the secondapplication; capturing, by the computing device, the data from the firstapplication based on the determination of the data type to be capturedfrom the first application; and causing, by the computing device, thecaptured data to be accessible to the second application.
 17. The methodof claim 15, further comprising: detecting, by the computing device, acompletion of the execution of the second application; and returning, bythe computing device, to an execution of the first application based onthe completion of the execution of the second application.
 18. Themethod of claim 15, wherein the return to the execution of the firstapplication is based on providing a process identifier of the firstapplication to the second application in an instance in which thecomputing device has initiated the execution of the second application.19. The method of claim 15, wherein the detection of the completion ofthe execution of the second application is based on at least one of auser interaction signaling a task completion or a user-manipulation of abutton for the computing device.
 20. The method of claim 15, wherein thedisplay of the second user interface comprises prepopulating thecaptured data from the first application.